<!DOCTYPE html>
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
  <meta charset="UTF-8"/>
  <meta name="viewport" content="width=device-width, initial-scale=1"/>
  <title>bdep-config(1) bdep 0.17.0</title>

  <style type="text/css">
/* file      : common.css
 * license   : MIT; see accompanying LICENSE file
 */

html
{
  font-family: "Helvetica Neue", Helvetica, "Segoe UI", Arial, freesans, sans-serif;
  font-weight: normal;
  font-size: 18px;
  line-height: 1.4em;
  letter-spacing: 0.01em;

  color: #292929;
}

body {margin: 0;} /* There is non-0 default margin for body. */

/* See notes on what's going on here. */
body {min-width: 17em;}
@media only screen and (min-width: 360px)
{
  body {min-width: 19em;}
}

/*
 * Header (optional).
 */

#header-bar
{
  width: 100%;

  background: rgba(0, 0, 0, 0.04);
  border-bottom: 1px solid rgba(0, 0, 0, 0.2);

  padding: .4em 0 .42em 0;
  margin: 0 0 1.4em 0;
}

#header
{
  /* Same as in #content. */
  max-width: 41em;
  margin: 0 auto 0 auto;
  padding: 0 .4em 0 .4em;

  -webkit-box-sizing: border-box;
  -moz-box-sizing: border-box;
  box-sizing: border-box;

  width: 100%;
  display: table;
  border: none;
  border-collapse: collapse;
}

#header-logo, #header-menu
{
  display: table-cell;
  border: none;
  padding: 0;
  vertical-align: middle;
}

#header-logo {text-align: left;}
#header-menu {text-align: right;}

/* These overlap with #header's margin because of border collapsing. */
#header-logo {padding-left: .4em;}
#header-menu {padding-right: .4em;}

#header-logo a
{
  color: #000;
  text-decoration: none;
  outline: none;
}
#header-logo a:visited {color: #000;}
#header-logo a:hover, #header-logo a:active {color: #000;}

#header-menu a
{
  font-size: 0.889em;
  line-height: 1.4em;
  text-align: right;
  margin-left: 1.2em;
  white-space: nowrap;
  letter-spacing: 0;
}

#header-menu a
{
  color: #000;
  outline: none;
}
#header-menu a:visited {color: #000;}
#header-menu a:hover, #header-menu a:active
{
  color: #3870c0;
  text-decoration: none;
}

/* Flexbox-based improvements though the above works reasonably well. */
#header-menu-body
{
  width: 100%;

  display: -webkit-inline-flex;
  display: inline-flex;

  -webkit-flex-flow: row wrap;
  flex-flow: row wrap;

  -webkit-justify-content: flex-end;
  justify-content: flex-end;
}

/* Whether we want it (and at which point) depends on the size of the menu. */
/*
@media only screen and (max-width: 567px)
{
  #header-menu-body
  {
    -webkit-flex-direction: column;
    flex-direction: column;
  }
}
*/

/*
 * Content.
 */

#content
{
  max-width: 41em;
  margin: 0 auto 0 auto;
  padding: 0 .4em 0 .4em; /* Space between text and browser frame. */

  -webkit-box-sizing: border-box;
  -moz-box-sizing: border-box;
  box-sizing: border-box;
}

/*
 * Footer (optional).
 */

#footer
{
  color: #767676;
  font-size: 0.7223em;
  line-height: 1.3em;
  margin: 2.2em 0 1em 0;
  text-align: center;
}

#footer a
{
  color: #767676;
  text-decoration: underline;
}
#footer a:visited {color: #767676;}
#footer a:hover, #footer a:active {color: #3870c0;}

/* Screen size indicator in the footer. The before/after content is in case
   we don't have any content in the footer. Margin is to actually see the
   border separate from the browser frame. */

/*
#footer:before {content: "\A0";}
#footer:after {content: "\A0";}

#footer
{
  border-left: 1px solid;
  border-right: 1px solid;
  margin-left: 1px;
  margin-right: 1px;
}

@media only screen and (max-width: 359px)
{
  #footer {border-color: red;}
}

@media only screen and (min-width: 360px) and (max-width: 567px)
{
  #footer {border-color: orange;}
}

@media only screen and (min-width: 568px) and (max-width: 1023px)
{
  #footer {border-color: blue;}
}

@media only screen and (min-width: 1024px)
{
  #footer {border-color: green;}
}
*/

/*
 * Common elements.
 */

p, li, dd {text-align: justify;}
.code {text-align: left;} /* Manually aligned. */
pre {text-align: left;}   /* If it is inside li/dd. */

/* Notes. */

.note
{
  color: #606060;
}

div.note
{
  margin: 2em 0 2em 0; /* The same top/bottom margings as pre box. */

  padding-left: 0.5em;
  border: 0.25em;
  border-left-style: solid;
  border-color: #808080;

  page-break-inside: avoid;
}

div.note :first-child {margin-top:    0;}
div.note :last-child  {margin-bottom: 0;}

span.note::before {content: "[Note: "}
span.note::after  {content: "]"}

/* Links. */
a
{
  color: #3870c0;
  /*color: #4078c0;*/
  text-decoration: none;
}

a:hover, a:active
{
/*color: #006fbf;*/
/*color: #0087e7;*/
  text-decoration: underline;
}

a:visited
{
/*color: #003388;*/
  color: #00409c;
}

/* Standard paragraph. */

p, pre {margin: 1em 0 1em 0;}

/* Standard lists. */
ul, ol, dl {margin: 1em 0 1em 0;}
ul li, ol li {margin: 0 0 .4em 0;}
ul li {list-style-type: circle;}
dl dt {margin: 0 0 0 0;}
dl dd {margin: 0 0 .6em 1.8em;}

code, pre
{
  font-family: Consolas, "Liberation Mono", Menlo, Courier, monospace;
  font-size: 0.92em;
  letter-spacing: 0;
}

pre {white-space: pre-wrap;}
@media only screen and (max-width: 567px)
{
  pre {word-break: break-all;}
}

/* Use page rather than system font settings. */
input
{
  font-family: inherit;
  font-weight: inherit;
  font-size:   inherit;
  line-height: inherit;
}

/* file      : pre-box.css
 * license   : MIT; see accompanying LICENSE file
 */

/* Note: see also p-code-box.css. */

pre
{
  background-color: rgba(0, 0, 0, 0.05);
  border-radius: 0.2em;
  padding: .8em .4em .8em .4em;
  margin: 2em -.4em 2em -.4em; /* Use margins of #content. */
}

/* file      : man.css
 * license   : MIT; see accompanying LICENSE file
 */

/* Bases:
 *
 * common.css
 * pre-box.css
 *
 */

#content
{
  max-width: 42.1em;
  padding-left: 1.5em; /* Reserve for the heading. */
}

h1
{
  font-weight: normal;
  font-size: 1.58em;
  line-height: 1.4em;
  margin: 1.6em 0 .6em -.88em;
}

/* Definition list for options. */
dl.options dt {margin: 1em 0 0 0;}
dl.options dd {margin: .1em 0 0 4.5em;}

/* Make lists inside option descriptions a tad smaller. */
dl.options dd ul, dl.options dd ol, dl.options dd dl
{
  font-size: 0.889em;
  line-height: 1.4em;
}

  </style>

</head>
<body>
<div id="content">

  <h1>NAME</h1>

  <p><b><code>bdep-config</code></b> &#8211; manage project build configurations</p>
  <h1>SYNOPSIS</h1>

  <p class="code"><code><b>bdep config add</b>
  &#160;&#160;&#160;[<i>options</i>] [<i>prj-spec</i>]
  [<b>@</b><i>cfg-name</i>] <i>cfg-dir</i>
  <br/>
  <b>bdep config create</b> [<i>options</i>] [<i>prj-spec</i>]
  [<b>@</b><i>cfg-name</i>] <i>cfg-dir</i> [<i>cfg-args</i>]
  <br/>
  <b>bdep config link</b> &#160;&#160;[<i>options</i>] [<i>prj-spec</i>]
  <i>cfg-spec</i> <i>cfg-spec</i>
  <br/>
  <b>bdep config unlink</b> [<i>options</i>] [<i>prj-spec</i>] <i>cfg-spec</i>
  <i>cfg-spec</i>
  <br/>
  <b>bdep config list</b> &#160;&#160;[<i>options</i>] [<i>prj-spec</i>]
  [<i>cfg-spec</i>...]
  <br/>
  <b>bdep config move</b> &#160;&#160;[<i>options</i>] [<i>prj-spec</i>]
  <i>cfg-spec</i> <i>cfg-dir</i>
  <br/>
  <b>bdep config rename</b> [<i>options</i>] [<i>prj-spec</i>] <i>cfg-spec</i>
  <i>cfg-name</i>
  <br/>
  <b>bdep config remove</b> [<i>options</i>] [<i>prj-spec</i>]
  <i>cfg-spec</i>... | <b>--all</b>|<b>-a</b>
  <br/>
  <b>bdep config set</b> &#160;&#160;&#160;[<i>options</i>] [<i>prj-spec</i>]
  <i>cfg-spec</i>... | <b>--all</b>|<b>-a</b>
  <br/>
  &#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;[<b>--</b>[<b>no-</b>]<b>default</b>]
  <br/>
  &#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;[<b>--</b>[<b>no-</b>]<b>forward</b>]
  <br/>
  &#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;[<b>--</b>[<b>no-</b>]<b>auto-sync</b>]</code></p>

  <p class="code"><code><i>cfg-spec</i> = <b>@</b><i>cfg-name</i> |
  <b>--config</b>|<b>-c</b> <i>cfg-dir</i>
  <br/>
  <i>prj-spec</i> = <b>--directory</b>|<b>-d</b> <i>prj-dir</i>
  <br/>
  <i>cfg-args</i> = [<b>--</b> [<i>bpkg-options</i>]]
  [<b>--existing</b>|<b>-e</b> | (<i>module</i> |
  <i>cfg-var</i>)...]</code></p>

  <h1>DESCRIPTION</h1>

  <p>The <code><b>config</b></code> command provides the following subcommands
  for managing project's build configurations. If no project directory is
  specified, then the current working directory is assumed.</p>

  <h1>CONFIG SUBCOMMANDS</h1>

  <dl>
  <dt><code><b>add</b></code></dt>
  <dd></dd>

  <dt><code><b>create</b></code></dt>
  <dd>The <code><b>add</b></code> subcommand adds an existing <a
  href="../../bpkg/doc/bpkg.xhtml"><code><b>bpkg(1)</b></code></a> build
  configuration in directory <code><i>cfg-dir</i></code> to the project's
  build configuration set. The <code><b>create</b></code> subcommand creates a
  new configuration in directory <code><i>cfg-dir</i></code> by executing the
  <a
  href="../../bpkg/doc/bpkg-cfg-create.xhtml"><code><b>bpkg-cfg-create(1)</b></code></a>
  command and passing to it <code><i>cfg-args</i></code>, if any. It then
  proceeds as <code><b>add</b></code> by adding the new configuration to the
  project's build configuration set.

  <p>In both subcommands, if <code><i>cfg-name</i></code> is specified, then
  the added configuration is given this name. Several <code><b>bdep</b></code>
  commands can use such names as a more convenient way to specify build
  configurations (see <a
  href="bdep-projects-configs.xhtml"><code><b>bdep-projects-configs(1)</b></code></a>
  for details).</p>

  <p>As a shortcut, if <code><i>cfg-name</i></code> is not specified and
  <code><i>cfg-dir</i></code> is a simple path that starts with
  <code><b>@</b></code>, then it is treated as the name and the configuration
  directory is assumed to be
  <code><i>prj-dir</i><b>-</b><i>cfg-name</i></code>. Note that in case of
  <code>create</code>, <code><i>cfg-dir</i></code> must be preceded with
  <code><b>--</b></code> (double dash) option to disambiguate it from
  <code><b>@</b><i>cfg-name</i></code>. For example, assuming the project
  directory is <code><b>hello</b></code>:</p>

  <pre>$ bdep config add @clang                        # ../hello-clang
$ bdep config create -- @gcc cc config.cxx=g++  # ../hello-gcc</pre>

  <p>A configuration also has a type that is specified with the
  <code><b>--type</b></code> option (or <code><b>--config-type</b></code> from
  <a href="bdep-new.xhtml"><code><b>bdep-new(1)</b></code></a>). If the type
  is not specified explicitly, then <code><b>target</b></code> is assumed. See
  <a
  href="../../bpkg/doc/bpkg-cfg-create.xhtml"><code><b>bpkg-cfg-create(1)</b></code></a>
  for background on configuration types.</p>

  <p>Unless the <code><b>--no-default</b></code> option is specified, the
  first added or created build configuration of each type is designated as the
  default. Several <code><b>bdep</b></code> commands use such a configuration
  by default if no configuration was specified explicitly (see <a
  href="bdep-projects-configs.xhtml"><code><b>bdep-projects-configs(1)</b></code></a>
  for details). To make a subsequently added configuration the default use the
  <code><b>--default</b></code> option. Note also that in case of multiple
  default configurations any given package within a project can only be
  initialized in one such configuration.</p>

  <p>The default build configuration of each type is also designated as
  forwarded unless the <code><b>--no-forward</b></code> option is specified or
  another configuration of this type is already designated as forwarded. When
  a project is initialized in a forwarded build configuration, its source
  directory is configured to forward to this configuration (see <a
  href="../../build2/doc/b.xhtml"><code><b>b(1)</b></code></a> for details on
  forwarded configurations). To designate a non-default configuration as
  forwarded use the <code><b>--forward</b></code> option. Note also that it is
  possible to have multiple forwarded configurations, however, any given
  package within a project can only be initialized in one such
  configuration.</p>

  <p>Unless the <code><b>--no-auto-sync</b></code> option is specified, an
  added or created build configuration will be automatically synchronized on
  every build system invocation. Note that this flag affects the entire build
  configuration and if multiple projects share the same configuration, then
  they must have a consistent auto-synchronization setting.</p></dd>

  <dt><code><b>link</b></code></dt>
  <dd>The <code><b>link</b></code> subcommand links the first specified build
  configuration with the second by executing the <a
  href="../../bpkg/doc/bpkg-cfg-link.xhtml"><code><b>bpkg-cfg-link(1)</b></code></a>
  command. See <a
  href="../../bpkg/doc/bpkg-cfg-create.xhtml"><code><b>bpkg-cfg-create(1)</b></code></a>
  for background on linked configurations.</dd>

  <dt><code><b>unlink</b></code></dt>
  <dd>The <code><b>unlink</b></code> subcommand unlinks the first specified
  build configuration from the second by executing the <a
  href="../../bpkg/doc/bpkg-cfg-unlink.xhtml"><code><b>bpkg-cfg-unlink(1)</b></code></a>
  command. See <a
  href="../../bpkg/doc/bpkg-cfg-create.xhtml"><code><b>bpkg-cfg-create(1)</b></code></a>
  for background on linked configurations.</dd>

  <dt><code><b>list</b></code></dt>
  <dd>The <code><b>list</b></code> subcommand prints the list of build
  configurations associated with the project. Unless one or more
  configurations are specified explicitly, <code><b>list</b></code> prints all
  the associate configurations. Note that the output is written to
  <code><b>stdout</b></code>, not <code><b>stderr</b></code>.

  <p>If the output format is <code><b>json</b></code> (see the
  <code><b>--stdout-format</b></code> common option), then the output is a
  JSON array of objects which are the serialized representation of the
  following C++ <code><b>struct</b></code>
  <code><b>configuration</b></code>:</p>

  <pre>struct package
{
  string name;
};

struct configuration
{
  uint64_t         id;
  string           path;
  optional&lt;string> name;
  string           type;
  bool             default;
  bool             forward;
  bool             auto_sync;
  vector&lt;package>  packages;
};</pre>

  <p>For example:</p>

  <pre>[
  {
    "id": 1,
    "path": "/tmp/hello-gcc",
    "name": "gcc",
    "type": "target",
    "default": true,
    "forward": true,
    "auto_sync": true,
    "packages": [
      {
        "name": "hello"
      }
    ]
  }
]</pre>

  <p>See the JSON OUTPUT section in <a
  href="bdep-common-options.xhtml"><code><b>bdep-common-options(1)</b></code></a>
  for details on the overall properties of this format and the semantics of
  the <code><b>struct</b></code> serialization.</p>

  <p>The <code><b>id</b></code> member is a numeric configuration id that can
  be used to identify the configuration instead of the name or path (see the
  <code><b>--config-id</b></code> option). The <code><b>path</b></code> member
  is an absolute path to the configuration directory. The
  <code><b>packages</b></code> member contains the array of packages belonging
  to this project that have been initialized in this configuration. See the
  <code><b>create</b></code> subcommand for the meaning of other members
  (<code><b>name</b></code>, <code><b>type</b></code>,
  <code><b>default</b></code>, etc).</p></dd>

  <dt><code><b>move</b></code></dt>
  <dd>The <code><b>move</b></code> subcommand assigns the specified build
  configuration a new directory. It is normally used after moving/renaming the
  configuration directory. Note that an explicit <a
  href="bdep-sync.xhtml"><code><b>bdep-sync(1)</b></code></a> command is
  required for this change to take effect. See <a
  href="bdep-projects-configs.xhtml"><code><b>bdep-projects-configs(1)</b></code></a>
  for various ways to specify a build configuration.</dd>

  <dt><code><b>rename</b></code></dt>
  <dd>The <code><b>rename</b></code> subcommand gives the specified build
  configuration a new name. See <a
  href="bdep-projects-configs.xhtml"><code><b>bdep-projects-configs(1)</b></code></a>
  for various ways to specify a build configuration.</dd>

  <dt><code><b>remove</b></code></dt>
  <dd>The <code><b>remove</b></code> subcommand removes one or more build
  configurations from the project's build configuration set. Note that only
  configurations that have no initialized packages can be removed. See <a
  href="bdep-projects-configs.xhtml"><code><b>bdep-projects-configs(1)</b></code></a>
  for various ways to specify build configurations.</dd>

  <dt><code><b>set</b></code></dt>
  <dd>The <code><b>set</b></code> subcommand modifies various properties of
  one or more build configurations associated with the project. See <a
  href="bdep-projects-configs.xhtml"><code><b>bdep-projects-configs(1)</b></code></a>
  for various ways to specify build configurations.

  <p>The properties that can be modified include the default
  (<code><b>--</b>[<b>no-</b>]<b>default</b></code>), forward
  (<code><b>--</b>[<b>no-</b>]<b>forward</b></code>), and auto-synchronization
  (<code><b>--</b>[<b>no-</b>]<b>auto-sync</b></code>) flags. Note that
  changing any of these flags requires an explicit <a
  href="bdep-sync.xhtml"><code><b>bdep-sync(1)</b></code></a> command to take
  effect.</p></dd>
  </dl>

  <h1>CONFIG OPTIONS</h1>

  <dl class="options">
    <dt><code><b>--type</b></code>|<code><b>--config-type</b></code> <code><i>typ</i></code></dt>
    <dd>The type of the configuration being created. By default, configuration
    of type <code><b>target</b></code> is created. See <a
    href="../../bpkg/doc/bpkg-cfg-create.xhtml"><code><b>bpkg-cfg-create(1)</b></code></a>
    for background on configuration types.</dd>

    <dt><code><b>--default</b></code></dt>
    <dd>Make the added or created configuration the default.</dd>

    <dt><code><b>--no-default</b></code></dt>
    <dd>Don't make the first added or created configuration the default.</dd>

    <dt><code><b>--forward</b></code></dt>
    <dd>Make the added or created configuration forwarded.</dd>

    <dt><code><b>--no-forward</b></code></dt>
    <dd>Don't make the added or created configuration forwarded.</dd>

    <dt><code><b>--auto-sync</b></code></dt>
    <dd>Make the added or created configuration automatically
    synchronized.</dd>

    <dt><code><b>--no-auto-sync</b></code></dt>
    <dd>Don't make the added or created configuration automatically
    synchronized.</dd>

    <dt><code><b>--existing</b></code>|<code><b>-e</b></code></dt>
    <dd>Initialize a <code><b>bpkg</b></code> configuration based on an
    existing build system configuration.</dd>

    <dt><code><b>--wipe</b></code></dt>
    <dd>Wipe the configuration directory clean before creating the new
    configuration.</dd>

    <dt><code><b>--all</b></code>|<code><b>-a</b></code></dt>
    <dd>Use all build configurations.</dd>

    <dt><code><b>--config</b></code>|<code><b>-c</b></code> <code><i>dir</i></code></dt>
    <dd>Specify the build configuration as a directory.</dd>

    <dt><code><b>--directory</b></code>|<code><b>-d</b></code> <code><i>dir</i></code></dt>
    <dd>Assume project/package is in the specified directory rather than in
    the current working directory.</dd>

    <dt><code><b>--config-name</b></code>|<code><b>-n</b></code> <code><i>name</i></code></dt>
    <dd>Specify the build configuration as a name.</dd>

    <dt><code><b>--config-id</b></code> <code><i>num</i></code></dt>
    <dd>Specify the build configuration as an id.</dd>
  </dl>

  <h1>COMMON OPTIONS</h1>

  <p>The common options are summarized below with a more detailed description
  available in <a
  href="bdep-common-options.xhtml"><code><b>bdep-common-options(1)</b></code></a>.</p>

  <dl class="options">
    <dt><code><b>-v</b></code></dt>
    <dd>Print essential underlying commands being executed.</dd>

    <dt><code><b>-V</b></code></dt>
    <dd>Print all underlying commands being executed.</dd>

    <dt><code><b>--quiet</b></code>|<code><b>-q</b></code></dt>
    <dd>Run quietly, only printing error messages.</dd>

    <dt><code><b>--verbose</b></code> <code><i>level</i></code></dt>
    <dd>Set the diagnostics verbosity to <code><i>level</i></code> between 0
    and 6.</dd>

    <dt><code><b>--stdout-format</b></code> <code><i>format</i></code></dt>
    <dd>Representation format to use for printing to
    <code><b>stdout</b></code>.</dd>

    <dt><code><b>--jobs</b></code>|<code><b>-j</b></code> <code><i>num</i></code></dt>
    <dd>Number of jobs to perform in parallel.</dd>

    <dt><code><b>--progress</b></code></dt>
    <dd>Display progress indicators for long-lasting operations, such as
    network transfers, building, etc.</dd>

    <dt><code><b>--no-progress</b></code></dt>
    <dd>Suppress progress indicators for long-lasting operations, such as
    network transfers, building, etc.</dd>

    <dt><code><b>--diag-color</b></code></dt>
    <dd>Use color in diagnostics.</dd>

    <dt><code><b>--no-diag-color</b></code></dt>
    <dd>Don't use color in diagnostics.</dd>

    <dt><code><b>--bpkg</b></code> <code><i>path</i></code></dt>
    <dd>The package manager program to be used for build configuration
    management.</dd>

    <dt><code><b>--bpkg-option</b></code> <code><i>opt</i></code></dt>
    <dd>Additional option to be passed to the package manager program.</dd>

    <dt><code><b>--build</b></code> <code><i>path</i></code></dt>
    <dd>The build program to be used to build packages.</dd>

    <dt><code><b>--build-option</b></code> <code><i>opt</i></code></dt>
    <dd>Additional option to be passed to the build program.</dd>

    <dt><code><b>--curl</b></code> <code><i>path</i></code></dt>
    <dd>The curl program to be used for network operations.</dd>

    <dt><code><b>--curl-option</b></code> <code><i>opt</i></code></dt>
    <dd>Additional option to be passed to the curl program.</dd>

    <dt><code><b>--pager</b></code> <code><i>path</i></code></dt>
    <dd>The pager program to be used to show long text.</dd>

    <dt><code><b>--pager-option</b></code> <code><i>opt</i></code></dt>
    <dd>Additional option to be passed to the pager program.</dd>

    <dt><code><b>--options-file</b></code> <code><i>file</i></code></dt>
    <dd>Read additional options from <code><i>file</i></code>.</dd>

    <dt><code><b>--default-options</b></code> <code><i>dir</i></code></dt>
    <dd>The directory to load additional default options files from.</dd>

    <dt><code><b>--no-default-options</b></code></dt>
    <dd>Don't load default options files.</dd>
  </dl>

  <h1>DEFAULT OPTIONS FILES</h1>

  <p>See <a
  href="bdep-default-options-files.xhtml"><code><b>bdep-default-options-files(1)</b></code></a>
  for an overview of the default options files. For the
  <code><b>config</b></code> command the search start directory is the project
  directory. The following options files are searched for in each directory
  and, if found, loaded in the order listed:</p>

  <pre>bdep.options
bdep-config.options
bdep-config-add.options          # if the create subcommand
bdep-config-&lt;subcommand>.options # (subcommand-dependent)</pre>

  <p>The following <code><b>config</b></code> command options cannot be
  specified in the default options files:</p>

  <pre>--directory|-d
--wipe</pre>

  <h1>BUGS</h1>

  <p>Send bug reports to the
  <a href="mailto:users@build2.org">users@build2.org</a> mailing list.</p>

</div>

<div id="footer">
Copyright &#169; 2014-2024 the build2 authors.<br/>
Permission is granted to copy, distribute and/or modify this document under
the terms of the MIT License.
</div>

</body>
</html>
